I currently still see the issue of not being able to follow the about-us link.

Dockerfile

from node:22.17.0

cmd ["bash", "-lc", "cd /code && npm install && npm run build && cd build && npx http-server -p 8001"]

run the container

docker run -v ./Local-Connectivity-Lab.github.io:/code -p 8001:8001

go to localhost:8001/about-us
it does not load.

There should be a file called about-us flat in the /build directory I assume?

The issue does not have to do with the type of static file server because both the python and the npx static file server give a 404

npx http-server -p 8001
python3 -m http.server 8001

Also it has been really hard to figure out how to run the tests locally, I still have not yet. Can you add a github action that runs the tests so we dont have to rely on our own machine?

Just tried again, and I am not getting the about-us not loading issue, but me and Ted seem to have found another issue

Run a static file server on port 5173

npx http-server -p 5173

Then in a different terminal run the tests

npm run test

The donate test fails.

You can verify this by going to the donate page directly http://localhost:5173/donate it will try to redirect forever

Also it has been really hard to figure out how to run the tests locally, I still have not yet. Can you add a github action that runs the tests so we dont have to rely on our own machine?

I'd like to address this post launch, and I've created an issue for it: #27

Run a static file server on port 5173

npx http-server -p 5173

Then in a different terminal run the tests

npm run test

The donate test fails.

You can verify this by going to the donate page directly http://localhost:5173/donate it will try to redirect forever

This should now be fixed

NPM audit appears to produce 1 low and 2 high risk vulnerabilities but these do not appear to be easilly exploitable if we are just generating a static website

Run a static file server on port 5173

npx http-server -p 5173

Then in a different terminal run the tests

npm run test

The donate test fails.
You can verify this by going to the donate page directly http://localhost:5173/donate it will try to redirect forever

This should now be fixed

I cannot reproduce this anymore!

I dont think it is secure to be able to run the CI whenever we want because if someone puts a piece of maleware in the next version of an NPM package and we did not audit it before we ran the CI again, we will be pushing security issues. If it is run at merge time, I would have ran npm audit or something before I approved. I do not approve of this change.

@kevinkace @abacef Kevin, Mark - let's discuss at the meeting. Kaylee and I are on now, Kevin is eating but will be here at 6:30p if not earlier.